Relay network for encryption system

ABSTRACT

A method comprises registering, by a first device having a public key, with a gateway server by providing a proof of work based on the first device public key and encrypting and decrypting data using cryptographic information transmitted via the gateway server between other devices similarly registered.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. provisional patentapplication No. 62/913,846 filed on Oct. 11, 2019, and titled “RelayNetwork,” which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

The disclosed teachings generally relate to data encryption and/ordecryption. The disclosed teachings more particularly relate to relayingdata between devices in an encryption system.

BACKGROUND

Conventionally, encryption systems rely only one or two devices toencrypt and decrypt files. However, when multiple devices are used forencryption and decryption, data may not be transferred efficientlybetween devices.

SUMMARY

Embodiments provide a method, computing device that can execute themethod and a computer-readable storage device having instructions forexecuting the method. The embodiments may enable more efficienttransmission of data in an encryption system. A method comprisesregistering, by a first device having a public key, with a gatewayserver by providing a proof of work based on the first device public keyand encrypting and/or decrypting data using cryptographic informationtransmitted via the gateway server between other devices similarlyregistered.

For example, encrypting data with a first device's symmetric key (e.g.,key for a symmetric cipher); generating, with a threshold cryptographydata-sharing scheme, a plurality of key shards based on the symmetrickey such that the symmetric key can be reconstituted from less than allof the plurality of key shards; encrypting the plurality of key shardswith public keys from, respectively, a plurality of devices;transmitting, through the gateway, the encrypted plurality of key shardsand encrypted data to at least one queue in a queue service, whereinthere is one queue for each device of the plurality of devices;triggering a cloud message from a cloud message service to one or moredevices of the plurality of devices corresponding to the at least onequeue, thereby causing the one or more devices to connect to a networkhosting the queue service; transmitting the encrypted plurality of keyshards and encrypted data from the queue service to the one or moredevices corresponding to the at least one queue; and storing theencrypted data and the plurality of key shards encrypted with theplurality of devices' public keys in one or more non-transitory memorydevices such that the encrypted data is secured at one of the one ormore non-transitory memory devices and decryptable with the plurality ofkey shards encrypted with the first devices' public keys by reassemblingthe plurality of key shards encrypted with the plurality of devices'public keys into the first device's symmetric key.

This Summary is provided to introduce a selection of concepts in asimplified form that is further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the embodied subject matter, nor is it intended tobe used to limit the scope of the embodied subject matter. Other aspectsof the disclosed embodiments will be apparent from the accompanyingFigures and Detailed Description.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention are illustrated by wayof example and not limitation in the figures of the accompanyingdrawings, in which like references indicate similar elements.

FIG. 1 is a block diagram that illustrates a system for implementingpasswordless encryption of data-at-rest according to some embodiments ofthe present disclosure;

FIG. 2 is a flow diagram that illustrates various processes forpasswordless security of data-at-rest according to some embodiments ofthe present disclosure;

FIG. 3 is a block diagram of an example process for generating keyshards, based on a cryptographic key, of which a threshold number can beused to reconstitute a cryptographic key according to some embodimentsof the present disclosure;

FIG. 4 is a block diagram illustrating an archive file according to someembodiments of the present disclosure;

FIG. 5 is a block diagram of an example key shard redistribution processaccording to some embodiments of the present disclosure;

FIG. 6 is a block diagram that illustrates components of an originatingdevice operable to secure data-at-rest according to some embodiments ofthe present disclosure;

FIG. 7 is a block diagram illustrating a data flow among components ofan originating device according to some embodiments of the presentdisclosure;

FIG. 8 is a flow diagram that illustrates a secure third-party channel(STPC) device linking according to some embodiments of the presentdisclosure;

FIG. 9 is a block diagram that illustrates a setup process of onboardingprocedures according to some embodiments of the present disclosure;

FIG. 10 is a block diagram of a computing device operable to implementaspects of the disclosed embodiments;

FIG. 11 is a block diagram of a system operable to implement aspects ofthe disclosed embodiments;

FIG. 12 is a block diagram of a packet for use in the system of FIG. 11;

FIG. 13 is a flow diagram illustrating a method of connecting to anetwork according to an embodiment; and

FIG. 14 is a flow diagram illustrating a method of transmitting data viathe connected network.

DETAILED DESCRIPTION

The embodiments set forth below represent the necessary information toenable those skilled in the art to practice the embodiments andillustrate the best mode of practicing the embodiments. Upon reading thefollowing description in light of the accompanying figures, thoseskilled in the art will understand the concepts of the disclosure andwill recognize applications of these concepts that are not particularlyaddressed herein. It should be understood that these concepts andapplications fall within the scope of the disclosure and theaccompanying claims.

The purpose of terminology used herein is only for describingembodiments and is not intended to limit the scope of the disclosure.Where context permits, words using the singular or plural form may alsoinclude the plural or singular form, respectively.

Terms such as “processing,” “computing,” “calculating,” “determining,”“displaying,” “generating” or the like, unless specifically statedotherwise, may refer to actions and processes of a computing device thatmanipulates and transforms data represented as physical (electronic)quantities within the computer's memory or registers into other datasimilarly represented as physical quantities within the computer'smemory, registers, or other such storage medium, transmission, ordisplay devices.

The terms “connected,” “coupled,” or variants thereof, as used herein,may refer to any connection or coupling, either direct or indirect,between two or more elements. The coupling or connection between theelements can be physical, logical, or a combination thereof.

The terms “channel” or “link” contemplate a means of communicating dataor information, whether wired or wireless, and may utilize digitalcellular transmission standards (e.g., CDMA, W-CDMA, LTE, HSPA+).Examples include Bluetooth, Wi-Fi, Ethernet, USB, USB-C, Thunderbolt,auditory link, or visual link (e.g., QR code and camera). A message maybe communicated directly between two devices or indirectly throughanother device (e.g., a relay device) on one or more channels/links.

The term “target data,” as used herein, may refer to data targeted forencryption. Examples of target data may include photos, documents,spreadsheets, audio files, video files, or any type of encryptable datafiles. Other examples include data stored in database tables, passwords,emails stored on a computer, or any data object.

The disclosed embodiments include techniques for securing data stored ona memory of a computing device. In some embodiments, a method includesencrypting data stored on a memory of a computing device with a blockcipher using cryptographic key(s). Several key shards can be generatedbased on any of the cryptographic key(s) via a threshold cryptographydata-sharing scheme. In some embodiments, each key shard of acryptographic key can be encrypted with its own unique public key. Anencrypted shard can be distributed to one of an array of physicallydistinct computing devices, which can each have a private key for itsencrypted key shard. The cryptographic key can be reconstituted with athreshold number of computing devices that utilize their private keys todecrypt their respective key shards. Specifically, the threshold numberof decrypted key shards can be used to reconstitute the cryptographickey, which can then be used to decrypt the encrypted data.

In conventional systems, a significant portion of data-at-rest that isstored at a computing device is not encrypted by default because of thechallenges associated with password and cryptographic key management.Maintaining a sufficient quantity of unique keys and passwords toadequately secure all target data is challenging in any system, fromconsumer-grade to enterprise level. Home and enterprise users needaccess to hundreds or even thousands of individual data objects on aregular basis, and are unable to memorize or adequately keep track ofmany high-entropy passwords that would be required to secure targetdata. Accordingly, users are reluctant to embrace additional passwordsfor data encryption because they are already inundated with passwordsfor different sites, services, and apps.

A solution to securing large volumes of data-at-rest includes using asingle master password as a key to decrypt numerous data objects storedin a container (e.g., a folder) stored in memory. This type of datasecurity system is vulnerable to attack and, if compromised, will exposethe numerous data objects with the single master password. For example,password manager tools such as DASHLANE and LASTPASS utilize a singlepassword which, if compromised, would provide an attacker with access toall the data encrypted with that single password. The risk growsexponentially due to increased efforts in computer hacking and theproliferation of viruses, malware, and ransomware developed by badactors to exploit vulnerabilities of existing key and passwordmanagement tools.

Securing data-at-rest is complicated by the risk of losing keys orpasswords. Unfortunately, users have grown accustomed to passwordretrieval mechanisms of websites such that they expect the ability toreset lost passwords that secure their data-at-rest. For example, when auser loses a password to access data of an enterprise system, the userexpects that a network administrator can readily send a reset link orcode to facilitate resetting the lost password. However, password resetsare not possible in the context of encryption of data-at-rest because adecryption algorithm cannot be performed without access to the key orpassword. A solution to this problem includes so-called “back doors,”which have been utilized to provide emergency access to data when a keyor password is lost. However, the back doors create vulnerabilities thatcan be exploited by bad actors. Due to these limitations, mostindividual users and enterprises do not encrypt the vast majority oftheir data-at-rest.

Another solution is full-disk encryption, which has been utilized toprovide security for physical loss or theft of hard drives. However,full-disk encryption does not protect against computer viruses, malware,ransomware or hackers who are able to gain control of a system. In anenterprise, if data-at-rest is encrypted, central management ofencryption keys is often utilized to enable recovery of data whenpasswords are misplaced, lost, or forgotten. However, a centralizedsystem creates a vulnerability as a treasure-trove of keys forattackers. In addition, full-disk encryption does not protect user data(e.g., email) stored on third-party platforms such as remote cloudstorage providers.

The disclosed embodiments overcome the drawbacks of conventional systemsby enabling the ability to secure large volumes of data-at-rest with“passwordless” encryption. Hence, unlike conventional systems, thedisclosed embodiments do not necessarily require a user to undertake theburdensome step of inputting a password to access any data-at-rest. Infact, each data object can be encrypted with a separate uniquecryptographic key that users are not required to explicitly store,memorize, manage, and safeguard to later decrypt any of the encrypteddata objects. Instead, the disclosed embodiments require limited andperiodic involvement by a user to decrypt any number of data objectswhile securing each data object with a block cipher using a uniquecryptographic key. A “cryptographic key” or “key,” as used herein, mayrefer to a string of bits used by a cipher to transform plain text intocipher text or vice versa. The key remains private and ensures securestorage and communication until the decryption event.

As described in greater detail below, a number of key shards can begenerated based on a cryptographic key of a block cipher used to encrypta data object. In some embodiments, the key shards are derived from thecryptographic key via a threshold cryptography data-sharing scheme. Thekey shards may be, for example, portions of a cryptographic key thatcollectively form the cryptographic key such that assembling the keyshards would reconstitute the cryptographic key. While embodiments aredescribed herein generally in the context of data-at-rest, files, ordata objects in general, those skilled in the art will appreciate thatthe various embodiments could include implementations for databaseentries, smartphone files (e.g., image files), emails contained in aninbox (e.g., email on a MS Exchange server or in a Gmail inbox), etc.

The disclosed embodiments can include combinations of hardware and/orsoftware. For example, an embodiment includes a security service thatcan operate on data stored on a computer storage medium. In anotherexample, an embodiment can include an application distinct from anoperating system or file system to separately operate on the data storedin the file system. In yet another example, an embodiment is integratedinto an existing file system to provide a simplified interface to usersfor readily storing an accessing encrypted data-at-rest.

FIG. 1 is a block diagram that illustrates a system for implementingpasswordless encryption of data-at-rest according to some embodiments ofthe present disclosure. As shown, the system 100 includes componentssuch as an originating device 102, a relay server 104, and an array ofdelegate devices 106 n. The originating device 102 can communicate overlink 112 a with the relay server 104, which can communicate with thedelegate devices 106 n over links 112 n. In some embodiments, thecomponents of the system 100 communicate as part of a security serviceof the originating device 102. In some embodiments, the originatingdevice 102 and the delegate devices 106 n can bypass the relay server104 to communicate over a link 112 b such as, for example, a wirelessradio link (e.g., BLUETOOTH) or some other direct or indirect means ofcommunication.

An “originating device,” as used herein, is a computing device fromwhich data-at-rest can be accessed. The data-at-rest can be stored at alocal memory of the originating device 102 or stored at a remotelylocated memory of another computing device. In some embodiments, anoriginating device is a device on which new content is created orpreexisting content is modified. In some embodiments, an originatingdevice may be operated as a general-purpose computer runningspecial-purpose software or a special purpose hardware device.

Examples of an originating device include a computer, smart or dumbterminal, a point-of-sale (POS) device, network computer, set-top box,game player, mobile device, wireless device, wireless telephone,personal digital assistant, media (e.g., music and/or video) player,camera, information appliance, workstation, minicomputer, mainframecomputer, or any other device that can store or access data-at-rest.Specific examples of an originating device include a desktop computer,laptop computer (e.g., APPLE MACBOOK, LENOVO 440), smartphone (e.g.,APPLE IPHONE, SAMSUNG GALAXY, NOKIA LUMINA), tablet computer (e.g.,APPLE IPAD, SAMSUNG NOTE, AMAZON FIRE, MICROSOFT SURFACE), or any othercomputing device that can store or access data-at-rest. Although asingle originating device 102 in shown in system 100, the disclosedembodiments can include any number of originating devices.

The originating device 102 can access one or more memories that storedata. The memories can include non-volatile memory for storingdata-at-rest. For example, the originating device 102 may include oraccess memory that stores a file system or an email archive. Thememories can include volatile memory that stores data-in-use. In someembodiments, the memories include a local storage device and/orcloud-based storage device that can separately or collectively storedata objects. The storage devices may be removable or non-removablecomputer readable storage media such as magnetic hard disk drives,solid-state drives, network-attached storage, flash memory devices,optical drives, remote cloud storage, etc. Other types of storage mediathat can be used in exemplary operating environments include, but arenot limited to, magnetic tape cassettes, flash memory cards, DVDs,digital video tape, solid-state random-access memory (RAM), solid stateread-only memory (ROM), etc. The storage media are typically connectedto a system bus through a removable or non-removable memory interface.

In some embodiments, a special-purpose software application may beinstalled on the originating device 102 to practice elements of thedisclosed operations, and to facilitate communication with othercomponents of the system 100 including the relay server 104 and thedelegate devices 106 n. In some embodiments, the originating device 102may also serve as a delegate device. A distinction between theoriginating device 102 and the delegate devices 106 n is there functionin the process of encrypting or decrypting data-at-rest with one or morecryptographic keys. In particular, the originating device 102 can accessthe encrypted data-at-rest stored in a local or remote memory and thedelegate devices 106 n can provide respective key shards used to derivethe cryptographic key for encrypting or decrypting the data-at-reststored by the originating device 102. As such, the delegate devices 106n can secure encrypted data-at-rest and authorize decryption of theencrypted data-at-rest by messaging key shards to the originating device102.

A “delegate device,” as used herein, may refer to a computing device onwhich private keys may be stored and on which key shards ofcryptographic keys may be stored. A “key shard,” as used herein, mayrefer to a data item of a threshold number of data items from which acryptographic key can be reconstituted (e.g., derived). The delegatedevices 106 n can include any combination of computing devices such asthose described herein with respect to the originating device 102.

The delegate devices 106 n may include any device that has beenconfigured, via software or hardware, to communicate securely with theoriginating device 102 (e.g., through the relay server 104) or among thedelegate devices 106 n. In some embodiments, the delegate devices 106 nare portable computing devices (e.g., smartphones, tablet devices,laptop devices) but can further include any device that is accessible tothe user and capable of communicating with the originating device 102 oramong the delegate devices 106 n. Examples include a desktop computer,smart or dumb terminal, a POS device, network computer, set top box,game player, mobile device, wireless device, wireless telephone,personal digital assistant, media player (e.g., music player, videoplayer), camera, information appliance, workstation, minicomputer,mainframe computer, or any other device with similar computingfunctionality.

The relay server 104 may securely deliver messages and notificationsbetween the originating device 102 and the delegate devices 106 n. Forexample, the relay server 104 may represent any number of servercomputers that can relay key shards between the originating device 102and the delegate device 106 n over the links 112 a-n. The user interfacemay be used to facilitate management of the encrypted data-at-rest bydistributing and collecting key shards among the delegate devices 106 n.In some embodiments, the relay server 104 may collect and store theencrypted data provided by the originating device 102 and/or thedelegate devices 106, and provide that data to any of the other devices.The relay server 104 may include a combination of hardware and softwarethat is well known to persons skilled in the art and, as such, adescription is omitted herein for the sake of brevity.

The links 112 a-n may include any combination of private, public, wired,or wireless portions. Any data communicated over the links 112 a-n maybe encrypted or unencrypted at various locations or along differentportions of the links 112 a-n. Each component of the system 100 mayinclude combinations of hardware and/or software to process the data,perform functions, communicate over the links 112 a-n, and the like. Forexample, any component of the system 100 may include a processor, memoryor storage, a network transceiver, a display, operating system, andapplication software (e.g., for providing a user interface), and thelike. Other components, hardware, and/or software included in the system100 that are well known to persons skilled in the art are not shown ordiscussed herein for the sake of brevity.

The ability to communicate over a wireless radio link 112 b (e.g.,BLUETOOTH, Wi-Fi) allows the originating device 102 to bypass the relayserver 104, to encrypt and decrypt data-at-rest by retrieving keyshard(s) directly from delegate device(s). Direct access by theoriginating device 102 to the delegate devices 106 n is useful when anyof the links 112 a or 112 n is down or inaccessible. Communicationlinks, particularly those established between the delegate devices 106 nand the originating device 102 may require modifications to the delegatedevices or information presented on a mobile device such as a quickresponse (QR) code. In some embodiments, all communications, regardlessof intermediary, are secured by encrypting data with the destinationdevice's public key.

Therefore, the system 100 can implement passwordless encryption ofdata-at-rest by using a combination of symmetric cryptography,asymmetric cryptography, and threshold cryptography implemented bymultiple computing devices. For example, advanced encryption standard(AES) or another cipher can be employed by the originating device 102.In some embodiments, the key shards are fragments of a cryptographic keythat are the outputs of a configurable threshold secret-sharing schemesuch as Shamir's secret sharing scheme, Blakley's scheme, or Chineseremainder theorem-based secret sharing. In some embodiments, the sharingscheme is operable to represent the cryptographic key with N fragmentsof which only M are required to reconstitute the original BCcryptographic key. Accordingly, the delegate devices 106 n can provide athreshold number of key shards required to reconstruct a cryptographickey. Thus, the originating device 102 can decrypt data by accessing thethreshold number of key shards rather than requiring input of thecryptographic key in its entirety.

FIG. 2 illustrates various processes of the disclosed passwordlesstechniques for securing data-at-rest. The disclosed techniques includethe use of a combination of symmetric cryptography, asymmetriccryptography, and configurable threshold cryptography to manageencryption and/or decryption of data-at-rest. The processes 200 can be aperformed by the originating device 102 and delegate devices 106 a-b aspart of a security service. The originating device 102 or delegatedevices 106 a-b can include a variety of different devices such as thosediscussed with reference to FIG. 1.

The originating device 102 and/or delegate devices 106 a-b may belong toa user that is authorized to access and decrypt data objects with theoriginating device 102. In some instances, at least some of the delegatedevices 106 a-b may belong to users that are not authorized to accessthe encrypted data. The memory storing the encrypted data may be a localmemory of the originating device 102 and/or a remote memory, and theencrypted data is stored on the local or remote memory.

In step 202, a user of the originating device 102 can designate a set ofcomputing devices as delegate devices 106 a or authorize a user of thedelegate devices 106 a. In some of the embodiments, each of the delegatedevices 106 a is physically separate from each other and/or couldinclude the originating device 102.

In step 204, the originating device 102 encrypts target data with acryptographic key. The cryptographic key may be created specifically toencrypt the target data. For example, the cryptographic key may be astring of bits of a symmetric key for use in a block cipher capable oftransforming plain text into cipher text and vice versa. In someembodiments, the cryptographic key is generated temporarily to encryptdata-at-rest and is thereafter deleted.

The target data may include various types of data objects (e.g., image,document, spreadsheet, audio file, video file) that are each encryptedwith respective cryptographic keys. Examples include a file system withvarious files and instructions for encrypting the files, an emailarchive system with emails and instructions for encrypting the emails, adatabase system records and instructions for encrypting the messages,etc. The encrypted target data is stored on a non-transitory computermemory that can be accessed by the originating device 102.

In step 206, the originating device 102 generates N key shards based onthe cryptographic key. The cryptographic key can be derived(reconstituted) from a necessary and sufficient threshold number M ofthe N key shards. For example, the set of N key shards can be generatedvia a threshold cryptography data-sharing scheme. When the user wants todecrypt the encrypted target data, M-of-N key shards are processed toreconstitute the cryptographic key. The set of key shards can be storedlocally and/or distributed among the delegate devices 106 a-b. As usedherein, a “key shard” of a cryptographic key may also be referred to asa component, fragment, or by any other term that indicates a part orelement of a set of key shards.

To aid in understanding data-sharing schemes, consider an W orderpolynomial that could be reconstituted from W+1 points of thatpolynomial. For example, consider a second order polynomialaX{circumflex over ( )}2+bX+c where the cryptographic key is representedby the constant term c. The polynomial can be reconstituted with anythree points of the polynomial. Examples of a sharing scheme includeShamir's Secret Sharing Scheme, Blakley's scheme, secret sharing usingthe Chinese remainder theorem, or any other sharing scheme understood bypersons skilled in the art. In one simple example, a cryptographic keysuch as the password “secret” can be used to encrypt target data, splitinto the shards “sec” and “ret,” and reassembled later to decrypt theencrypted target data.

For example, FIG. 3 is a block diagram of an example process forgenerating a set of key shards, based on a cryptographic key, of which athreshold number of the key shards can be used to reconstitute acryptographic key. As shown, device A is an originating device anddevices B through F are delegate devices. A set of key shards can bedistributed across combinations of the computing devices A, B, C, D, E,and/or F. The illustrated example is of a three-of-five configurationwhere only three key shards are required to reconstitute thecryptographic key and remaining devices are superfluous. Thus, losingaccess to any two-of-five computing devices B through F would notprevent the originating device 102 from reconstituting the cryptographickey because the key shards from the remaining computing devices aresufficient to do so. Note, however, that the cryptographic key cannot bereconstituted from a subset of the key shards that is less than thethreshold number (e.g., two key shards). The reconstituted cryptographickey can then be used to decrypt or encrypt data.

The disclosed embodiments include an asymmetric key pair that isgenerated for each delegate device 106 a. The key pair includes adelegate public key and a delegate private key. These two keys may becreated together using a key generation technique such as RSA orelliptic curve key pairs. The delegate asymmetric key pair may begenerated at a delegate device. The delegate private key may be keptexclusively on the delegate device and never shared or exported toanother computing device. In contrast, the delegate public key is sharedor exported for use by another delegate device or the originatingdevice. In some embodiments, the key shards can be encrypted with thedelegate public keys to produce encrypted key shards that can besecurely communicated to their delegate devices. The mechanism forencryption and the choice of key strength may be configurable and mayinclude, for example, RSA, ECIES, ElGamal and other encryption schemeswith similar functionality

Each delegate device may generate a delegate key pair including adelegate private key and delegate public key. Each delegate device canretain its respective delegate private key. For example, delegate deviceD1 could retain private key K-1, delegate device D2 could retain privatekey K-2, and so on. Each of the N delegate devices may also distributeits delegate public key to any other delegate device and eachoriginating device such that all delegate devices and originatingdevices have all the delegate public keys and originating device publickeys.

A backup key pair may be generated with a backup public key distributedto the various originating devices as well. The decision whether togenerate a backup public key may depend on user or administratorpreference. Hence, the disclosed embodiments may employ other key pairsthat improve security. For example, an embodiment may employ a backupasymmetric key pair, which includes a backup public key and a backupprivate key. These backup key pairs may be generated by a computingdevice when offline by using a key generation technique such as RSA orelliptic curve key generation. The backup private key can be kept on theoffline computer while the backup public key can be exported for use byother computing devices.

In step 208, each of the N key shard is encrypted with one of N publickeys associated with a respective delegate device to create N encryptedkey shards. In addition, any metadata associated with the original datais authenticated, for example via MAC or by including the metadata inthe shard. The originating device 102 may have access to all the publickeys of the delegate devices 106 a such that the originating device 102can use the public keys to encrypt the key shards for respectivedelegate devices 106 a. The delegate devices 106 a hold respectivecounterpart private keys that can be uses to decrypt their respectivekey shards as needed.

In some embodiments, the cryptographic key is optionally encrypted usinga backup public key to create an encrypted cryptographic key that can bedecrypted using a backup private key. The backup keys are generallycreated and stored in an offline environment. For example, a file system(FS) can encrypt the target data by using the cryptographic key. The FScan store the encrypted key shards with the encrypted target data in anarchive file on disk. In addition, if a backup public key was created,it may be used to encrypt the cryptographic key, which may then be addedto the archive file.

An “archive file,” as used herein, is a customized file format in whichtarget data that has been encrypted with, for example, a BC using acryptographic key may be stored together with any combination ofencrypted versions of the cryptographic key (or related keys), encryptedkey shards, or encrypted key sub-key shards. For example, FIG. 4 is ablock diagram that depicts an archive file 400 according to someembodiments of the present disclosure. The archive file 400 has a filestructure including a shard segment 402, and backup segment 404.

As shown, the archive file 400 may include an entire cryptographic keythat has been encrypted with a backup public key or another asymmetricencryption technique. Hence, decryption of an archive file may requireadditional cryptographic information to produce a decrypted version ofthe cryptographic key. In some instances, additional sets of encryptedkey shards are added in the archive file. The additional sets ofencrypted key shards may be used to open files. With the encrypted keyshards added to the archive file, the encryption process is complete. Insome embodiments, at least some of the encrypted key shards areoptionally sent to the delegate devices 106 a to further improvesecurity. Optionally distributing the N encrypted key shards to thedelegate devices 106 a reduces the network traffic required to decryptdata and redistribute shards. Encrypted target data is recoverable withthe key shards stored at the delegate devices 106 a.

For example, in step 210 of FIG. 2, the N encrypted key shards aredistributed among the first set of delegate devices 106 a such that theoriginating device 102 is incapable of decrypting the encrypted targetdata due to an absence of a cryptographic key and the keys shards fromwhich the cryptographic key can be reconstituted. For example, theoriginating device can communicate with a relay server to distribute theshards among the delegate devices 106 a.

In some embodiments, distributing the N encrypted key shards involvesestablishing a wireless link (e.g., Wi-Fi, BLUETOOTH, cellular), a wiredlink (e.g., Ethernet, USB), visual link, or auditory link between theoriginating device 102 and the delegate devices 106 a. For example, atleast one of the N key shards can be communicated over a computernetwork to at least one of the set of delegate devices 106 a that areremotely located from the originating device 102. In another example, atleast one of the N key shards is communicated over a short-range radiolink to at least one of the set of delegate devices 106 a that islocated remote from the originating device 102. The delegate devices 106a may be temporarily or intermittently coupled to the originating device102 to communicate the key shards.

In some embodiments, a local security service can extract a set ofencrypted key shards from an archive file. The originating device 102may pass the set of encrypted key shards to a communication service,which distributes the encrypted shards to respective delegate devices.Communication among the delegate devices 106 a may be direct (e.g., onthe same LAN, via BLUETOOTH or Ethernet connection) or via a relayserver or onion routing scheme.

Key Shard Redistribution Process

The disclosed embodiments include a key shard redistribution process toreplace or add a delegate device to an existing set of delegate devices.If an existing delegate device is lost, stolen, destroyed, renderedobsolete, or is otherwise inaccessible, it can be replaced with anotherdelegate device according to the redistribution process. In someembodiments, the threshold number of key shards required to reconstitutea cryptographic key may be the same or different from the thresholdnumber of key shards required for the redistribution process. Moreover,the redistribution process can be used to change the threshold number ofdevices required to reconstitute a cryptographic key.

In step 214, the optional redistribution process is performed togenerate a second set of key shards based on a combination of the firstset of key shards. The second set of key shards is generated from afirst threshold number of the first set of key shards, and may includesome or none of the first set of key shards. The number of the secondset of key shards may be the same or different than the first set of keyshards. The cryptographic key is capable of being reconstituted fromeither the first set of key shards or the second set of key shards.Further, the second set of key shards may be generated without everreconstituting the cryptographic key.

In some embodiments, the redistribution process involves generatingintermediary sub-key shards from the first set of key shards, and thengenerating the second set of key shards from the sub-key shards. Thesub-key shards are distributed among the second combination of devicesthat can generate the second set of key shards based on the sub-keyshards. As such, a type and number of the first set of delegate devicesthat holds the first set of key shards can change to a second set ofdelegate devices that holds the second set of key shards. Hence, thesecond combination of delegate devices may include some or none of thefirst combination of delegate devices.

FIG. 5 is a block diagram that illustrates an example process forgenerating new key shards from a threshold number of existing key shardssuch that a cryptographic key can be reconstituted from a new thresholdnumber of the new key shards according to some embodiments of thepresent disclosure. In the illustrated example, a three-of-fiveconfiguration is required to perform the redistribution process and toreconstitute the cryptographic key. That is, only three key shards arerequired to replace any number of the first set of delegate devices andonly three new key shards are required to reconstitute the cryptographickey.

The redistribution process requires decrypting only a threshold numberof encrypted key shards. The threshold number of unencrypted key shardsmay be made available from the archive file or from the respectivedelegate devices on which they reside. The threshold number ofunencrypted shards are inputs to a redistribution process that producesa new set of unencrypted key shards, which can be encrypted with theprivate keys of the second set of delegate devices (including any newdelegate devices), resulting in more encrypted key shards compared tothe original number of key shards. The new encrypted key shards can beadded to the archive file of the originating device and may bedistributed to additional delegate devices.

As shown, the originating device A generates five key shards based on acryptographic key, and distributes the five key shards to the first setof delegate devices B through F. The device B is a primary delegatedevice (e.g., user's smartphone), and the delegate devices C through Fare backup delegate devices (e.g., each a tablet computer). Assume thatdevices B and/or C are lost or otherwise inaccessible. A user canoperate a GUI on the originating device A (or a remaining delegatedevice) to trigger a redistribution process to the new delegate devicesB′ through F′.

A set of sub-key shards are created as an intermediate step in theprocess to create the new set of key shards for the second set ofdelegate devices B′ through F′. As used herein, “sub-key shards” mayrefer to key shards generated based on other key shards and which havebeen created in accordance with a redistribution process that extendsthe sharing scheme to create a new set of key shards from a preexistingsubset of a threshold number of key shards. Of the new set of keyshards, only another threshold number may be required to reconstitutethe original cryptographic key. Therefore, the new threshold and newnumber of key shards need not be the same as the original threshold andoriginal number of key shards, respectively.

As shown, the originating device A works in consort with the delegatedevices D, E, and F to produce sub-key shards for the delegate devicesB′ through F′. The delegate device D will produce sub-key shards D-1through D-5, the delegate device E will produce sub-key shards E-1through E-5, and the delegate device F will produce sub-key shards F-1through F-5. The sub-key shards D-1, E-1, and F-1 are for the newdelegate device B′. The sub-key shards D-2, E-2, and F-2 are for the newdelegate device C′. The sub-key shards D-3, E-3, and F-3 are for the newdelegate device D′. The sub-key shards D-4, E-4, and F-4 are for the newdelegate device E′, and the sub-key shards D-5, E-5, and F-5 are for thenew delegate device F′. The new key shards are derived from the sub-keyshards at the respective new delegate devices B′ through F′.

Therefore, the new set of delegate devices B′ through F′ replace the oldset of delegate devices B through F. The new key shards may be encryptedwith the respective public key of the delegate devices B′ through F′.The new encrypted key shards can be added to the archive file of theoriginating device A, and may be distributed to other remaining delegatedevices. Except for the missing shards, the remaining encrypted keyshards may be made available at the archive files or at respectivedelegate devices on which they reside. There is no need to reconstitutethe cryptographic key during the redistribution process, nor arethree-of-five decrypted shards required at any device during theredistribution process. Instead, the cryptographic key only needs to bereconstituted to decrypt or encrypt target data. Further, a minimumthreshold number of delegate devices and respective key shards areneeded to reconstitute the cryptographic key. In this instance,three-of-five new key shards are required to reconstitute thecryptographic key.

The ability to limit the need to reconstitute the cryptographic key onlyto decrypt or encrypt target data improves the security of the targetdata. For example, needing to reconstitute cryptographic keys fornumerous data objects to create new sets of key shards is undesirablebecause this would create a vulnerability. In particular, a bad actorthat knows that a redistribution process will occur because the badactor stole a delegate device could snoop to capture cryptographic keysfor data object during that process. Hence, the embodiments mitigate therisk of this vulnerability by avoiding the need to reconstitute anycryptographic key except to encrypt or decrypt data objects.

Although FIG. 5 illustrates a process for replacing an entire first setof delegate devices with the second set, the redistribution process canbe utilized to replace any number of delegate devices, as long as thethreshold number of the original delegate devices are available for theredistribution of key shards. Moreover, the redistribution process canbe used to add an infinite number of different combinations of delegatedevices. For example, consider a situation where the first set ofdelegate devices only includes D, E, and F. After performing aredistribution process, the second set of delegate devices may includeB′, C′, D, E, and F.

Therefore, the disclosed embodiments include techniques forincorporating other computing devices into a set that stores key shards.This includes adding or replacing selected computing devices to create anew combination of computing devices that store the set of key shardsrequired to reconstitute a cryptographic key from the threshold numberof key shards, and then re-sharding the cryptographic key to generate anew set of key shards for a new combination of computing devices.

Decryption Process

In step 216, the decryption process may be invoked when a user of theoriginating device 102 attempts to open a file, read data from adatabase, or otherwise access an encrypted data object. For example, afile opening process may be interrupted by a file system (FS) handler oroperating system handler, which recognizes the file that contains theencrypted data object. In some embodiments, the originating device 102collects at least the threshold number of decrypted key shards from thedelegate devices 106 a and/or 106 b. For example, the originating device102 can cause the delegate device 106 a-b to communicate theirrespective key shards to the originating device 102.

In some embodiments, the delegate devices 106 a-b can check with usersin possession of respective delegate devices as to whether to permit thedecryption event. The request for permission may be presented in avariety of forms such as a text or SMS message, a popup notification,LED display, or other format built-in to the operating system orprovided by system software and available hardware. The user may acceptthe request for a decryption event. In some embodiments, a request isautomatically denied after a predetermined period expires.

In an M-of-N configuration, only a threshold M of the total N key shardsare required to reconstitute a cryptographic key. Of the N correspondingdelegate devices, one or more are primary (i.e., authorizing) devicesand the remainder are secondary devices. For example, in a 2-of-3configuration in which there is a laptop, a smartphone, and a tablet,the laptop could be the originating device, the smartphone could be theprimary delegate device, and the tablet could be a delegate secondarydevice. In this example, reassembly of the cryptographic key requiresparticipation by only two devices: the originating device and thesmartphone. Participation by a secondary device is not necessary unlessthe primary delegate device is unavailable.

In some embodiments, a user in possession of a delegate device may,contingent on the name, type, path or other target data metadata, set athreshold for a number of automatic affirmative responses to requestsfor decryption. For example, the threshold may be set to automaticallydecrypt the next 10 shards received or automatically decrypt all shardsreceived during the next 12 hours. If decryption is permitted, thedelegate device can decrypt its respective encrypted key shard andreturn the decrypted key shard to the originating device 102 via a relayserver or other communication channel, or can be re-encrypted fortransit to the originating device 102. The key shards received by theoriginating device can be used to reconstitute the cryptographic key,which is delivered to the FS or operating system. The target data maythen be decrypted and opened.

In step 218, the originating device 102 reconstitutes a cryptographickey from key shards collected from the originating device 102 and/or thedelegate devices 106 a-b. In some embodiments, at least some or all ofthe key shards are required to reconstitute the cryptographic key.Specifically, the cryptographic key is reconstituted from a thresholdnumber of the key shards collected from the originating device 102and/or the delegate devices 106 a-b. Then, in step 220, the originatingdevice decrypts the encrypted target data stored on a non-transitorycomputer memory with the reconstituted cryptographic key.

In some embodiments, any reconstituted cryptographic keys are enabledfor only a period sufficient to decrypt the encrypted data. For example,in step 222, any reconstituted cryptographic keys are automaticallydeleted after completing decryption of the encrypted target data. Insome embodiments, a cryptographic key and any copies of key shards aremade inoperable or deleted from the originating device 102 such that anycryptographic key for decrypting the encrypted data is unavailable orunderivable except during decryption or encryption of target data.

The disclosed embodiments also include a process for modifying encrypteddata. The data that has been encrypted according to the encryptionprocess described herein can be decrypted according to the decryptionprocess described herein. The decrypted data can then be modified, andagain encrypted according to the encryption process described herein.

The disclosed embodiments also include a key rotation process. Forexample, a user or a system may wish to rotate or change thecryptographic keys used for encrypting target data. Key rotation can beaccomplished by decrypting the target data by using a firstcryptographic key in the decryption process described herein and thenre-encrypting the target data by using the encryption process describedherein, but with a second cryptographic key that is different from thefirst cryptographic key.

The originating device may be operating under the control of anoperating system that provides a file system, which controls how data isstored and retrieved. In some embodiments, the originating device may beconfigured to run a virtual file system (VFS), an interface layer orabstraction layer that insulates the application program from the filesystem implementation, and can provide a common interface to multipletypes of file systems. If a VFS is utilized, the VFS can respond toapplication-level calls for file operations including opening, reading,writing, and appending to files stored on the device. The VFS can alsorespond to handling encryption events applicable for each fileoperation. If the originating device is not running a VFS, theoriginating device's operating system may respond directly toapplication-level calls for file operations and handling encryptionevents applicable for each file operation.

For example, FIG. 6 is a block diagram that illustrates components of anoriginating device operable to perform at least some of the processes200. For example, the originating device may include a graphical userinterface (GUI) module 602 that facilitates interactions with a user.The originating device may also include a security service 604, a filesystem 606, and various functions accessible or available via API calls608 and 610. Tasks such as adding or removing a delegate device, systemconfiguration, controlling alerts, and other features may be managed bya user through the GUI module 602.

In some embodiments, the originating device's security service 604 is aprogram that runs at an originating device, though it could be runningelsewhere such as on a dedicated server. For example, the securityservice can accept requests from a file system (e.g., virtual filesystem (VFS), a file system built into the computer's operating system,a customized file system or otherwise) to reconstitute a cryptographickey used to decrypt content of an archive file. In some embodiments, thesecurity service is part of a special-purpose software applicationinstalled on the originating device to enable the disclosedcryptographic operations and facilitate communications with a relayserver and/or delegate device.

FIG. 7 is a block diagram illustrating a data flow among components ofan originating device according to some embodiments of the presentdisclosure. The security service 702 may control communication via arelay network, key storage, and key management. The security service 702is communicatively coupled to the file system 704 (e.g., VFS) and theGUI module 706. As an example, the security service 702 may communicatemessages and notifications across a relay network related to generating,updating, and sharing credentials.

In some embodiments, a cryptographic process starts with a user or aprogram attempting to open a file located in a file system 704. The filesystem 704 could appear as a folder within a user's home directory. Fromthe user's perspective, the file system 104 could operate like otherfolders on the originating device. On the back end, the files within thefile system 704 folder are data stored in an encrypted manner withinarchive files. The user need not be aware of the archive files nor theiractual location, which could be in cloud storage, on a file server, orboth on the local device with the data mirrored on a cloud server (e.g.,DROPBOX, GOOGLE DRIVE).

The file system 704 (as a virtual file system) may manage interactionswith the file system of the originating device's storage device. Anapplication programming interface (API) may be provided to permitcommunications among the modules in the originating device. For example,the file system 704 can communicate with the security service 702 thatthe file system 704 needs a key to decrypt data in an archive file. Thesecurity service 702 then contacts the various delegate devices,retrieves relevant key shards, reconstitutes the cryptographic key, anddelivers the reconstituted cryptographic key to the file system 704. Thefile system 704 can then decrypt the data in the archive file. In someembodiments, the file system 704 will usually pass the relevantencrypted key shards found within the archive file to the securityservice 702. The security service 702 can then send those encrypted keyshards to a relay server for eventual receipt by relevant delegatedevices. The relevant delegate devices, using their respective privatekeys, can decrypt the encrypted key shards, and return unencrypted keyshards to the security service 702, which can reconstitute thecryptographic key and return it to the file system 704. The file system704 can use the reconstituted cryptographic key to decrypt the datastored in the archive file and then present the decrypted data to therelevant program.

In some embodiments, the archive file may not contain certain associatedencrypted key shards. The missing key shards could be stored only ondelegate devices. Under those circumstances, the security service 702can instruct delegate devices to produce relevant key shards by using areference number for the archive file.

The security service 702 may also be responsible for producing newcryptographic keys for the file system 704 (e.g., upon creation of a newfile), using a sharing scheme to create key shards, and encrypting thosekey shards with public keys of respective delegate devices. Theencrypted key shards can be sent to the delegate devices, and also sentback to the file system 704 for storage within the archive file.

The security service 702 can also interact with the GUI module 706 tohandle with several operations including loss or removal of a delegatedevice, the replacement or addition of a delegate device, and change thenumber of either M or N key shards. These operations may require aredistribution of key shards in accordance with the key shardredistribution process described herein.

The security service 702 can interact with the GUI module 706 to processa change in the user's delegate devices for authorization or backuppurposes. For example, an implementation may have a 2-of-4configuration, meaning that at least two of four computing devices thatstore respective distributed key shards are required to assemble acryptographic key that enables decryption of target data. The user'scomputing devices may include a laptop as an originating device, asmartphone as a primary delegate device, a tablet as a backup delegatedevice, and a friend's smartphone as another backup delegate device. Allfour devices store respective encrypted key shards and the associatedprivate key required for decryption. Under normal circumstances, theuser will only receive decryption requests on the user's primarydelegate device, and the originating device will provide decrypted keyshards by default. If the battery of the user's primary delegate device(e.g., smartphone) is discharged, the user may wish to switch the dutyof the primary delegate device temporarily to the backup delegate device(e.g., tablet). Switching to the backup delegate device would notrequire a redistribution operation but could require communication viathe relay server.

Setup Process

The disclosed embodiments include processes for securely linking devicesto exchange data such as key shards. For example, FIG. 8 is a flowdiagram illustrating a secure third-party channel (STPC) device linkingprocess 800 according to some embodiments of the present disclosure.More specifically, process 800 implements a secure communication channelfor the exchange of public keys.

In step 802, a client device (a first device) can request a securechannel type (e.g., QR, email, SMS) by selecting a channel and thensending its device ID such as, for example, a random 16-byte one timekey and a hash of its public key to the authorizing device (a seconddevice). In step 804, the authorizing device requests the clientdevice's public key. In step 806, the client device initiates sendingthe public key to the authorizing device. Lastly, in step 808, theauthorizing device sends a reply message with an authentication deviceID, one-time key (OTK), and public key to complete the secure exchangerequired to establish a secure link between the devices.

FIG. 9 is a block diagram that depicts a setup process for onboardingprocedures according to some embodiments of the present disclosure.Stage 1 shows that an originating device can perform a secure exchangeof public keys with delegate devices via the usage of the STPC mechanismof FIG. 6. All communication after this can be encrypted and signed.Stage 2 shows that after linking with the delegate devices, theoriginating device can send the full on-boarding information to thedelegate devices which will link them to each other in stage 3. Thecompletion illustrated in stage 3 results in all devices exchangingtheir public keys with each other in a secure manner. The groupincluding the originating device and delegate devices are then ready tosecurely communicate key shards.

FIG. 10 is a block diagram of a computing device 1000 operable toimplement aspects of the disclosed embodiments. The computing device1000 may be a generic computer or specifically designed to carry outfeatures of the system 100. The computing device 1000 may be anoriginating device, a relay server, or a delegate device embodied as,for example, a system-on-chip (SOC), a single-board computer (SBC)system, a server, a desktop or laptop computer, a kiosk, a mainframe, amesh of computer systems, a handheld mobile device, or combinationsthereof.

The computing device 1000 may be a standalone device or part of adistributed system that spans multiple networks, locations, machines, orcombinations thereof. In some embodiments, the computing device 1000operates as a server computer (e.g., relay server) or a client device(e.g., originating device, delegate device) in a client-server networkenvironment, or as a peer machine in a peer-to-peer system. In someembodiments, the computing device 1000 may perform one or more steps ofthe disclosed embodiments in real-time, in near real-time, offline, bybatch processing, or combinations thereof.

As shown, the computing device 1000 includes a bus 1002 operable totransfer data between hardware components. These components include acontrol 1004 (i.e., processing system), a network interface 1006, anInput/Output (I/O) system 1008, and a clock system 1010. The computingdevice 1000 may include other components not shown or further discussedfor the sake of brevity. One having ordinary skill in the art willunderstand any hardware and software included but not shown in FIG. 10.

The control 1004 includes one or more processors 1012 (e.g., centralprocessing units (CPUs), application specific integrated circuits(ASICs), and/or field programmable gate arrays (FPGAs)) and memory 1014(which may include software 1016). The memory 1014 may include, forexample, volatile memory such as random-access memory (RAM) and/ornon-volatile memory such as read-only memory (ROM). The memory 1014 canbe local, remote, or distributed.

A software program (e.g., software 1016), when referred to as“implemented in a computer-readable storage medium,” includescomputer-readable instructions stored in a memory (e.g., memory 1014). Aprocessor (e.g., processor 1012) is “configured to execute a softwareprogram” when at least one value associated with the software program isstored in a register that is readable by the processor. In someembodiments, routines executed to implement the disclosed embodimentsmay be implemented as part of operating system (OS) software (e.g.,MICROSOFT WINDOWS, LINUX) or a specific software application, component,program, object, module or sequence of instructions referred to as“computer programs.”

As such, the computer programs typically comprise one or moreinstructions set at various times in various memory devices of acomputer (e.g., computing device 1000) and which, when read and executedby at least one processor (e.g., processor 1012), cause the computer toperform operations to execute features involving the various aspects ofthe disclosed embodiments. In some embodiments, a carrier containing theaforementioned computer program product is provided. The carrier is oneof an electronic signal, an optical signal, a radio signal, or anon-transitory computer-readable storage medium (e.g., memory 1014).

The network interface 1006 may include a modem or other interfaces (notshown) for coupling the computing device 1000 to other computers, forexample, over the network 1024. The I/O system 1008 may operate tocontrol various I/O devices, including peripheral devices such as adisplay system 1018 (e.g., a monitor or touch-sensitive display) and oneor more input devices 1020 (e.g., a keyboard and/or pointing device).Other I/O devices 1022 may include, for example, a disk drive, printer,scanner, or the like. Lastly, the clock system 1010 controls a timer foruse by the disclosed embodiments.

Operation of a memory device (e.g., memory 1014), such as a change instate from a binary one to a binary zero (or vice versa) may comprise avisually perceptible physical transformation. The transformation maycomprise a physical transformation of an article to a different state orthing. For example, a change in state may involve accumulation andstorage of charge or release of stored charge. Likewise, a change ofstate may comprise a physical change or transformation in magneticorientation, or a physical change or transformation in molecularstructure, such as from crystalline to amorphous or vice versa.

FIG. 11 is a block diagram of a system 1100 operable to implementaspects of the disclosed embodiments. The system 1100 comprises a queueservice having queues 1155, a cloud messaging token store 1120, a cloudmessaging service 1130, gateway servers 1140 and 1150, a load balancer1160, and a plurality of devices, e.g., A1 and A2. Note that two devicesare shown for ease of illustration and system 1100 may comprise morethan two devices. Similarly, while two gateway servers are shown,additional gateway servers can be added. The system 1100 is acommunication system which facilitates seamless peer-to-peer messaging.The system 1100 is designed to effectively transmit messages amongheterogeneous clients with speed and reliability, while scaling toaccommodate variable load. The system 1100 can be used in conjunctionwith the encryption methods disclosed above, e.g., encryption methodsdisclosed in conjunction with FIG. 2.

Devices A1 and A2 (which can be substantially similar to originatingdevice 102 and delegate devices 106 n) have unique public/private keypairs, where the private key is known only to the device that owns itand the public key is known by all other devices that wish tocommunicate with the device in question. Each client additionally has aclient identifier (CID) which is its unique address for the sake ofrouting messages in the system 1100. The CID may be derived from thepublic key in a number of ways, including:

-   -   Taking the SHA-256 hash of the PEM encoding of the public key    -   Directly using the public value(s) of the key, e.g. the curve        point for an elliptic curve key    -   Taking the SHA-256 hash of the public value(s) of the key

In an embodiment, the CID may be kept at a consistent and shortenedlength by using just the first 16 bytes of output from the above values.

Clients establish a connection to the system 1100 using its well-knownhostname, which can either directly resolve to a list of gateway serverIP addresses or points to the load balancer 1160. If used, the loadbalancer 1160 selects a gateway server (1140 or 1150) and forwards theconnection to that server. The gateway servers 1140, 1150 act asWebSocket servers and handle the client authentication process, as willbe discussed in conjunction with FIG. 12 below. They also interact withtheir connected devices Al and A2 and the described services and storesto facilitate message delivery. Since the gateway servers 1140, 1150 donot communicate with each other directly, capacity can be expandedsolely by adding more gateway servers, to the extent supported by theother components.

The queue service 1110 represents any system which can store orderedlists of messages, where each list has a separate identifier andrepresents a “queue.” Embodiments include:

-   -   Using a SQL database where each table is a queue    -   Using a SQL database and a single table, where the queue is        identified by a column value    -   Using a message queue product such as IBM MQ, Apache Kafka, or        Amazon SQS

All gateway servers connect to the same service without the need to knowabout its internal structure. Within the queue service 1110, there isone queue per device 1155, created by gateway servers 1140, 1150 at thetime the device is first known. This queues 1155 hold all of themessages destined for that device, and these messages may be kept in thequeue via a number of strategies:

-   -   Retain all messages indefinitely    -   Retain all messages for a set amount of time, such as 2 weeks    -   Variably retain messages based on their attributes, such as        message type or message priority    -   Messages may optionally be removed from a queue after having        been received by the client.

The Cloud Messaging (CM) service 1130, such as Firebase, is used todeliver notifications and wake-up messages to supported devices. Such adevice will have a unique CM token, which it provides during itsregistration. The CM token store 1120 is used to map CIDs to CM tokensfor the benefit of the gateway servers 1140, 1150. The servers 1140,1150 interact with the CM service 1130 using these tokens in order totrigger the necessary notifications and messages which are delivered todevices.

FIG. 12 is a block diagram of a packet 11200 for use in the system 1100.The packet includes fields such as message ID 1210, which can be usedfor deduplication and message confirmation/deletion; destination CID1220; message type 1230, indicating the nature of the message at anapplication level; message priority 1240, indicating how time-sensitivethe message is or what its retention strategy should be; other 1250 andthe actual payload 1260, which includes shards, public keys andencrypted data that is transmitted as discussed in conjunction with FIG.2. The payload 1260 may be opaque to the system 1260. These fields andthe payload may be combined and encoded via several strategies, such asJSON, BSON, and Protocol Buffers.

FIG. 13 is a flow diagram illustrating a method 1300 of connecting to anetwork according to an embodiment. The method 1300 comprises connectingto a gateway server 1310; encoding and transmitting 1320 a messagecomprising a public key, a client identifier of one of the plurality ofdevices, and a signature of a private key of at least one field of themessage; and verifying 1330 authenticity of the one of the plurality ofdevices by confirming the provided public key is valid, the signaturematches the public key, and client identifier matches the public key.

In order to connect to the system 1100, a device A1, A2 firstestablishes a WebSocket connection with one of the gateway servers 1140,1150, optionally using transport layer security (TLS). The device A1, A2then encodes and sends a message containing its public key and,optionally, its claimed CID. The message additionally contains asignature from the client's private key of pertinent fields of themessage such as the public key and the claimed CID. The server 1140,1150 decodes this message and verifies its authenticity by ensuringthat:

-   -   The provided public key is valid    -   The signature of the signed data matches the provided public key    -   The provided CID matches the public key per the steps described        above, if applicable

If all of the verifications succeed, the device A1, A2 is considered tobe registered under its CID. Registered devices are able to sendmessages over the system 1100 and will receive messages destined fortheir CID. If any of the registration verifications fail, the device A1,A2 will not be considered registered, will not be able to send orreceive messages, and may have its connection terminated by the server1140, 1150.

In an embodiment, a gateway server 1140 or 1150 can require proof ofwork for registration. In this embodiment, gateway server requires anM-bit proof of work in order to be used. The connecting device A1 or A2will be rejected if it fails to provide the correct proof of work. Aproof of work is exponential in difficulty depending on the number ofbits. Specifically, the connecting device A1 and A2 must repeatedly hashtheir public key with a nonce until the number of leading null bits ofthe hash are equivalent to the required proof. At any time, the servers1140, 1150 can reject a connection and require additional proof. Thiscan be done with bias toward IP address that are more heavily using thenetwork. In this way, the system 1100 can defend itself from denial ofservice attacks.

FIG. 14 is a flow diagram illustrating a method 1400 of transmittingdata via the connected network. Messages can be sent by any device A1,A2, etc. registered on a gateway server 1140, 1150. When a device isregistered, it will be sent any messages which arrive in that device'squeue. It is often impractical or impossible for a device to becontinuously connected to the system 1100, particularly when the clientis an application on a mobile phone. In this case, the system's 1100 useof CM allows the device to connect just when necessary. When a messagedestined for this device is received, the system 1100 determines if itwarrants use of CM based on the message type and/or message priority, asdescribed above. If it is warranted, the gateway server 1140, 1150triggers the CM 1130 service to send an CM message to the device. Thismessage need not have meaningful content, but primarily serves as atrigger for the device to connect to the system 1100 and retrieve itsmessages. This is effective on a mobile phone because the device haspersistent services which receive the CM messages and can deliver themto the mobile application, regardless of whether the application isalready running.

The method 1400 for message delivery from the device A1 to A2 comprises

1. Client A1 sends the message over the WebSocket with which it isconnected to its gateway server 1140.

2. Gateway server 1140 attempts to locate a queue for the recipient,device A2. If no such queue exists, it creates it. The server 1140 putsthe message in this queue via the queue service 1110.

3. Gateway server 1140 looks for an CM token for device A2 in the CMstore 1120.

4. If an CM token was found, gateway server 1140 sends a request to theCM service 1130 to trigger an CM message to the token.

5. Gateway server 1150 receives the message from A2's queue.

6. The CM service 1130 delivers the CM message to device A2. If A2 wasnot already connected to the system 1100, it uses this as a trigger toestablish a connection at this point.

7. Gateway server 1150 delivers the message to client B over itsWebSocket connection.

Note that if device A2 is not already connected to the system 1100, andthe device does not support CM or the CM message fails to be delivered,the message from A1 is not lost. Whenever A2 does connect to the system1100, its gateway server 1150 will retrieve messages from the queueservice and deliver the message at that time, assuming it has not passedits persistence period.

As mentioned above, the message can be in format of the packet 1200 andthe payload 1260 may include anything transmitted between devices asdescribed above, e.g, shards in FIG. 2.

Examples of the disclosed embodiments include:

1. A method, comprising:

-   registering, by a first device having a public key, with a gateway    server by providing a proof of work based on the first device public    key;-   encrypting data with a first device's symmetric key;-   generating, with a threshold cryptography data-sharing scheme, a    plurality of key shards based on the symmetric key such that the    symmetric key can be reconstituted from less than all of the    plurality of key shards;-   encrypting the plurality of key shards with public keys from,    respectively, a plurality of devices;-   transmitting, through the gateway, the encrypted plurality of key    shards and encrypted data to at least one queue in a queue service,    wherein there is one queue for each device of the plurality of    devices;-   triggering a cloud message from a cloud message service to one or    more devices of the plurality of devices corresponding to the at    least one queue, thereby causing the one or more devices to connect    to a network hosting the queue service;-   transmitting the encrypted plurality of key shards and encrypted    data from the queue service to the one or more devices corresponding    to the at least one queue; and-   storing the encrypted data and the plurality of key shards encrypted    with the plurality of devices' public keys in one or more    non-transitory memory devices such that the encrypted data is    secured at one of the one or more non-transitory memory devices and    decryptable with the plurality of key shards encrypted with the    first devices' public keys by reassembling the plurality of key    shards encrypted with the plurality of devices' public keys into the    first device's symmetric key.

2. The method of example 1, further comprising:

-   receiving, at the first device, a request to decrypt the data    encrypted with the symmetric key;-   retrieving shards of the symmetric key;-   requesting decryption by the plurality of devices of the shards    until a threshold number of shards is reached;-   reconstituting the symmetric key from the decrypted shards; and-   decrypting the encrypted data with the symmetric key;-   wherein the receiving shards and requesting decryption includes    transmitting shards and requests, respectively, via the at least one    queue and triggering cloud messages to the one or more devices    corresponding to the at least one queue.

3. The method of any of the preceding examples, further comprising:

-   retrieving at least one token from a cloud message store    corresponding to the at least one queue; and wherein the triggering    is in response to the retrieving.

4. The method of any of the preceding examples, wherein the transmittingto and from the at least one queue transmits the encrypted plurality ofkey shards and encrypted data in packets having a client identifieridentifying a destination device from the plurality of devices andcorresponding queue from the at least one queue.

5. The method of any of the preceding examples, further comprisinggenerating the client identifier by taking a SHA-256 hash privacyenhanced mail encoding of a public key of the destination device.

6. The method of any of the preceding examples, further comprisinggenerating the client identifier based on a curve point for an ellipticcurve key of the destination device.

7. The method of any of the preceding examples, further comprisinggenerating the client identifier by taking a SHA-256 HASH of a publickey of the destination device.

8. The method of any of the preceding examples, further comprising:

-   connecting to the gateway server;-   encoding and transmitting a message comprising a public key, a    client identifier of one of the plurality of devices, and a    signature of a private key of at least one field of the message; and-   verifying authenticity of the one of the plurality of devices by    confirming the public key from the transmitted message is valid, the    signature matches the public key, and client identifier matches the    public key.

9. The method of any of the preceding examples, further comprising loadbalancing the transmitting to and from the at least one queue with aload balancer.

10. A computer-readable medium having stored thereon instructions tocause to a computer to execute a method, the method comprising:

-   registering, by a first device having a public key, with a gateway    server by providing a proof of work based on the first device public    key;-   encrypting data with a first device's symmetric key;-   generating, with a threshold cryptography data-sharing scheme, a    plurality of key shards based on the symmetric key such that the    symmetric key can be reconstituted from less than all of the    plurality of key shards;-   encrypting the plurality of key shards with public keys from,    respectively, a plurality of devices;-   transmitting, through the gateway, the encrypted plurality of key    shards and encrypted data to at least one queue in a queue service,    wherein there is one queue for each device of the plurality of    devices;-   causing triggering a cloud message from a cloud message service to    one or more devices of the plurality of devices corresponding to the    at least one queue, thereby causing the one or more devices to    connect to a network hosting the queue service;-   causing transmitting the encrypted plurality of key shards and    encrypted data from the queue service to the one or more devices    corresponding to the at least one queue; and-   storing the encrypted data and the plurality of key shards encrypted    with the plurality of devices' public keys in one or more    non-transitory memory devices such that the encrypted data is    secured at one of the one or more non-transitory memory devices and    decryptable with the plurality of key shards encrypted with the    first devices' public keys by reassembling the plurality of key    shards encrypted with the plurality of devices' public keys into the    first device's symmetric key.

11. A computing device comprising:

-   a processor; and-   one or more memories that include instructions that, when executed    by the processor, cause the computing device to:-   register, by a first device having a public key, with a gateway    server by providing a proof of work based on the first device public    key;-   encrypt data with a first device's symmetric key;-   generate, with a threshold cryptography data-sharing scheme, a    plurality of key shards based on the symmetric key such that the    symmetric key can be reconstituted from less than all of the    plurality of key shards;-   encrypt the plurality of key shards with public keys from,    respectively, a plurality of devices;-   transmit, through the gateway, the encrypted plurality of key shards    and encrypted data to at least one queue in a queue service, wherein    there is one queue for each device of the plurality of devices;-   cause triggering a cloud message from a cloud message service to one    or more devices of the plurality of devices corresponding to the at    least one queue, thereby causing the one or more devices to connect    to a network hosting the queue service;-   cause transmitting the encrypted plurality of key shards and    encrypted data from the queue service to the one or more devices    corresponding to the at least one queue; and-   storing the encrypted data and the plurality of key shards encrypted    with the plurality of devices' public keys in one or more    non-transitory memory devices such that the encrypted data is    secured at one of the one or more non-transitory memory devices and    decryptable with the plurality of key shards encrypted with the    first devices' public keys by reassembling the plurality of key    shards encrypted with the plurality of devices' public keys into the    first device's symmetric key.

12. The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause:

-   receiving, at the first device, a request to decrypt the data    encrypted with the symmetric key;-   retrieving shards of the symmetric key;-   requesting decryption by the plurality of devices of the shards    until a threshold number of shards is reached;-   reconstituting the symmetric key from the decrypted shards; and-   decrypting the encrypted data with the symmetric key;-   wherein the receiving shards and requesting decryption includes    transmitting shards and requests, respectively, via the at least one    queue and triggering cloud messages to the one or more devices    corresponding to the at least one queue.

The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause:

-   retrieving at least one token from a cloud message store    corresponding to the at least one queue; and-   wherein the triggering is in response to the retrieving.

14. The computing device of any of the preceding examples, wherein thetransmitting to and from the at least one queue transmits the encryptedplurality of key shards and encrypted data in packets having a clientidentifier identifying a destination device from the plurality ofdevices and corresponding queue from the at least one queue.

15. The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause generating the clientidentifier by taking a SHA-256 hash privacy enhanced mail encoding of apublic key of the destination device.

16. The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause generating the clientidentifier based on a curve point for an elliptic curve key of thedestination device.

17. The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause generating the clientidentifier by taking a SHA-256 HASH of a public key of the destinationdevice.

18. The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause:

-   connecting to the gateway server;-   encoding and transmitting a message comprising a public key, a    client identifier of one of the plurality of devices, and a    signature of a private key of at least one field of the message; and-   verifying authenticity of the one of the plurality of devices by    confirming the public key from the transmitted message is valid, the    signature matches the public key, and client identifier matches the    public key.

19. The computing device of any of the preceding examples, wherein theinstructions, when executed, further cause load balancing thetransmitting to and from the at least one queue with a load balancer.

Although the described flowcharts can show operations as a sequentialprocess, many of the operations can be performed in parallel orconcurrently. In addition, the order of the operations may bere-arranged. A process is terminated when its operations are completed.A process may correspond to a method, a procedure, an algorithm, etc.The operations of methods may be performed in whole or in part, may beperformed in conjunction with some or all of the operations in othermethods, and may be performed by any number of different systems, suchas the systems described herein, or any portion thereof, such as aprocessor included in any of the systems.

Aspects of the disclosed embodiments may be described in terms ofalgorithms and symbolic representations of operations on data bitsstored on memory. These algorithmic descriptions and symbolicrepresentations generally include a sequence of operations leading to adesired result. The operations require physical manipulations ofphysical quantities. Usually, though not necessarily, these quantitiestake the form of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. Customarily,and for convenience, these signals are referred to as bits, values,elements, symbols, characters, terms, numbers, or the like. These andsimilar terms are associated with physical quantities and are merelyconvenient labels applied to these quantities.

While embodiments have been described in the context of fullyfunctioning computers, those skilled in the art will appreciate that thevarious embodiments are capable of being distributed as a programproduct in a variety of forms and that the disclosure applies equallyregardless of the particular type of machine or computer-readable mediaused to actually effect the embodiments.

While the disclosure has been described in terms of several embodiments,those skilled in the art will recognize that the disclosure is notlimited to the embodiments described herein and can be practiced withmodifications and alterations within the spirit and scope of theinvention. Those skilled in the art will also recognize improvements tothe embodiments of the present disclosure. All such improvements areconsidered within the scope of the claims disclosed herein. Thus, thedescription is to be regarded as illustrative instead of limiting.

What is claimed is:
 1. A method, comprising: registering, by a firstdevice having a public key and a symmetric key, with a gateway server byproviding a proof of work based on the first device's public key;encrypting data with the first device's symmetric key; generating, witha threshold cryptography data-sharing scheme, a plurality of key shardsbased on the symmetric key where the symmetric key can be reconstitutedfrom less than all of the plurality of key shards; encrypting theplurality of key shards with public keys from, respectively, a pluralityof devices; transmitting, through the gateway, the encrypted pluralityof key shards and encrypted data to at least one queue in a queueservice, wherein there is one queue for each device of the plurality ofdevices; triggering a cloud message from a cloud message service to oneor more devices of the plurality of devices corresponding to the atleast one queue, thereby causing the one or more devices to connect to anetwork hosting the queue service; transmitting the encrypted pluralityof key shards and encrypted data from the queue service to the one ormore devices corresponding to the at least one queue; and storing theencrypted data and the plurality of key shards encrypted with theplurality of devices' public keys in one or more non-transitory memorydevices where the encrypted data is secured at one of the one or morenon-transitory memory devices and decryptable with the plurality of keyshards encrypted with the first devices' public key by reassembling theplurality of key shards encrypted with the plurality of devices' publickeys into the first device's symmetric key.
 2. The method of claim 1,further comprising: receiving, at the first device, a request to decryptthe data encrypted with the symmetric key; retrieving shards of thesymmetric key; requesting decryption by the plurality of devices of theshards until a threshold number of shards is reached; reconstituting thesymmetric key from the decrypted shards; and decrypting the encrypteddata with the symmetric key; wherein the receiving shards and requestingdecryption includes transmitting shards and requests, respectively, viathe at least one queue and triggering cloud messages to the one or moredevices corresponding to the at least one queue.
 3. The method of claim1, further comprising: retrieving at least one token from a cloudmessage store corresponding to the at least one queue; and wherein thetriggering is in response to the retrieving.
 4. The method of claim 1,wherein the transmitting to and from the at least one queue transmitsthe encrypted plurality of key shards and encrypted data in packetshaving a client identifier identifying a destination device from theplurality of devices and corresponding queue from the at least onequeue.
 5. The method of claim 4, further comprising generating theclient identifier by taking a SHA-256 hash privacy enhanced mailencoding of a public key of the destination device.
 6. The method ofclaim 4, further comprising generating the client identifier based on acurve point for an elliptic curve key of the destination device.
 7. Themethod of claim 4, further comprising generating the client identifierby taking a SHA-256 HASH of a public key of the destination device. 8.The method of claim 4, further comprising: connecting to the gatewayserver; encoding and transmitting a message comprising a public key, aclient identifier of one of the plurality of devices, and a signature ofa private key of at least one field of the message; and verifyingauthenticity of the one of the plurality of devices by confirming thepublic key from the transmitted message is valid, the signature matchesthe public key, and the client identifier of one of the plurality ofdevices matches the public key.
 9. The method of claim 1, furthercomprising load balancing the transmitting to and from the at least onequeue with a load balancer.
 10. A non-transitory computer-readablemedium having stored thereon instructions to cause to a computer toexecute a method, the method comprising: registering, by a first devicehaving a public key and a symmetric key, with a gateway server byproviding a proof of work based on the first device's public key;encrypting data with the first device's symmetric key; generating, witha threshold cryptography data-sharing scheme, a plurality of key shardsbased on the symmetric key where the symmetric key can be reconstitutedfrom less than all of the plurality of key shards; encrypting theplurality of key shards with public keys from, respectively, a pluralityof devices; transmitting, through the gateway, the encrypted pluralityof key shards and encrypted data to at least one queue in a queueservice, wherein there is one queue for each device of the plurality ofdevices; causing triggering a cloud message from a cloud message serviceto one or more devices of the plurality of devices corresponding to theat least one queue, thereby causing the one or more devices to connectto a network hosting the queue service; causing transmitting theencrypted plurality of key shards and encrypted data from the queueservice to the one or more devices corresponding to the at least onequeue; and storing the encrypted data and the plurality of key shardsencrypted with the plurality of devices' public keys in one or morenon-transitory memory devices where the encrypted data is secured at oneof the one or more non-transitory memory devices and decryptable withthe plurality of key shards encrypted with the first devices' public keyby reassembling the plurality of key shards encrypted with the pluralityof devices' public keys into the first device's symmetric key.
 11. Afirst computing device comprising: a processor; and one or more memoriesthat include instructions that, when executed by the processor, causethe computing device to: register, by the first device, the first devicehaving a public key and a symmetric key, with a gateway server byproviding a proof of work based on the first device's public key;encrypt data with the first device's symmetric key; generate, with athreshold cryptography data-sharing scheme, a plurality of key shardsbased on the symmetric key where the symmetric key can be reconstitutedfrom less than all of the plurality of key shards; encrypt the pluralityof key shards with public keys from, respectively, a plurality ofdevices, each device comprising a processor; transmit, through thegateway, the encrypted plurality of key shards and encrypted data to atleast one queue in a queue service, wherein there is one queue for eachdevice of the plurality of devices; cause triggering a cloud messagefrom a cloud message service to one or more devices of the plurality ofdevices corresponding to the at least one queue, thereby causing the oneor more devices to connect to a network hosting the queue service; causetransmitting the encrypted plurality of key shards and encrypted datafrom the queue service to the one or more devices corresponding to theat least one queue; and storing the encrypted data and the plurality ofkey shards encrypted with the plurality of devices' public keys in oneor more non-transitory memory devices where the encrypted data issecured at one of the one or more non-transitory memory devices anddecryptable with the plurality of key shards encrypted with the firstdevices' public key by reassembling the plurality of key shardsencrypted with the plurality of devices' public keys into the firstdevice's symmetric key.
 12. The computing device of claim 11, whereinthe instructions, when executed, further cause: receiving, at the firstdevice, a request to decrypt the data encrypted with the symmetric key;retrieving shards of the symmetric key; requesting decryption by theplurality of devices of the shards until a threshold number of shards isreached; reconstituting the symmetric key from the decrypted shards; anddecrypting the encrypted data with the symmetric key; wherein thereceiving shards and requesting decryption includes transmitting shardsand requests, respectively, via the at least one queue and triggeringcloud messages to the one or more devices corresponding to the at leastone queue.
 13. The computing device of claim 11, wherein theinstructions, when executed, further cause: retrieving at least onetoken from a cloud message store corresponding to the at least onequeue; and wherein the triggering is in response to the retrieving. 14.The computing device of claim 11, wherein the transmitting to and fromthe at least one queue transmits the encrypted plurality of key shardsand encrypted data in packets having a client identifier identifying adestination device from the plurality of devices and corresponding queuefrom the at least one queue.
 15. The computing device of claim 14,wherein the instructions, when executed, further cause generating theclient identifier by taking a SHA-256 hash privacy enhanced mailencoding of a public key of the destination device.
 16. The computingdevice of claim 14, wherein the instructions, when executed, furthercause generating the client identifier based on a curve point for anelliptic curve key of the destination device.
 17. The computing deviceof claim 14, wherein the instructions, when executed, further causegenerating the client identifier by taking a SHA-256 HASH of a publickey of the destination device.
 18. The computing device of claim 14,wherein the instructions, when executed, further cause: connecting tothe gateway server; encoding and transmitting a message comprising apublic key, a client identifier of one of the plurality of devices, anda signature of a private key of at least one field of the message; andverifying authenticity of the one of the plurality of devices byconfirming the public key from the transmitted message is valid, thesignature matches the public key, and the client identifier of one ofthe plurality of devices matches the public key.
 19. The computingdevice of claim 11, wherein the instructions, when executed, furthercause load balancing the transmitting to and from the at least one queuewith a load balancer.